Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boards: xenvm: remove incorrect condition for Kconfig heap values #81790

Merged
merged 2 commits into from
Dec 5, 2024

Conversation

firscity
Copy link
Contributor

xenvm Kconfig contained incorrect name for board parameter. It led to build issues - heap size was set incorrectly. Since whole file is already placed under right Kconfig condition ("if BOARD_XENVM"), remove incorret parameter at all.

This issue was introduced by commit 8dc3f85 during migration to hwmv2 due to typo.

@firscity firscity requested a review from lorc November 22, 2024 17:26
@zephyrbot zephyrbot added size: XS A PR changing only a single line of code area: Xen Platform labels Nov 22, 2024
luca-fancellu
luca-fancellu previously approved these changes Nov 22, 2024
@firscity firscity force-pushed the board_xenvm_typo_fix branch from 77cf4e9 to fab0cd6 Compare November 22, 2024 17:30
lorc
lorc previously approved these changes Nov 22, 2024
kartben
kartben previously approved these changes Nov 22, 2024
nordicjm
nordicjm previously approved these changes Nov 25, 2024
@kartben
Copy link
Collaborator

kartben commented Nov 25, 2024

@firscity it looks like the CI failures might be legit?

@firscity
Copy link
Contributor Author

@kartben yeah, thank you
fixing of this issue highlighted another, I am currently trying to find best way to fix both in scope of this PR

@@ -7,7 +7,7 @@ tests:
kernel.device:
integration_platforms:
- native_sim
platform_exclude: xenvm
platform_exclude: xenvm xenvm/xenvm/gicv3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make all of these multiline please, this way diffs will be cleaner going forward

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for suggestion, done.

@firscity firscity force-pushed the board_xenvm_typo_fix branch from 9e1692b to aea83bc Compare November 25, 2024 20:26
kartben
kartben previously approved these changes Nov 25, 2024
@firscity
Copy link
Contributor Author

Thanks everyone for review and approves.

For everyone previously reviewed:
Adding changes to xenvm board triggered another issue with HWMv2 where invalid test were applied to newly introduced (by HWMv2) board. Additional commit added this board to excludes as it was made for xenvm.

Also I have no idea why net.mqtt_sn.packet test is failing, it doesn't look like smth that where caused by my changes.

lorc
lorc previously approved these changes Nov 25, 2024
@firscity
Copy link
Contributor Author

Hi @rlubos, as I can see, you are maintainer of net.mqtt_sn.packet test. It is failing unexpectedly during build, can you please check it? It looks like something not related to this PR.

@kartben
Copy link
Collaborator

kartben commented Nov 27, 2024

Hi @rlubos, as I can see, you are maintainer of net.mqtt_sn.packet test. It is failing unexpectedly during build, can you please check it? It looks like something not related to this PR.

This has been fixed in main. Please rebase to make the error go away:)

@firscity firscity force-pushed the board_xenvm_typo_fix branch from aea83bc to 1553ef5 Compare November 27, 2024 12:01
@firscity
Copy link
Contributor Author

@kartben yeah, thank you for information! Now everything looks good, @povergoing take a look please

@kartben
Copy link
Collaborator

kartben commented Dec 5, 2024

@povergoing ping

luca-fancellu
luca-fancellu previously approved these changes Dec 5, 2024
Copy link
Contributor

@luca-fancellu luca-fancellu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need another maintainer, @povergoing might not be active at the moment

cfriedt
cfriedt previously approved these changes Dec 5, 2024
@kartben kartben assigned kartben and lorc and unassigned kartben Dec 5, 2024
@kartben
Copy link
Collaborator

kartben commented Dec 5, 2024

I think you need another maintainer, @povergoing might not be active at the moment

Right. They should probably remove themselves as a maintainer then, based on their recent inactivity. Any other collaborator willing to step up as maintainers?
I've add you @lorc as an assignee to help keep this going
@firscity this needs another rebse.

xenvm Kconfig contained incorrect name for board parameter. It led to
build issues - heap size was set incorrectly. Since whole file is
already placed under right Kconfig condition ("if BOARD_XENVM"), remove
incorrect parameter at all.

This issue was introduced by commit 8dc3f85 ("hwmv2: Introduce
Hardware model version 2 and convert devices") due to the typo.

Signed-off-by: Dmytro Firsov <[email protected]>
The issue with mentioned test for GICv3 version of xenvm virtual
board is the same as for regular xenvm - device tree overlay for this
test overrides #address-cells and #size-cells property for original
device tree file (from 0x2 to 0x1), which leads to incorrect DT parsing
by actual Xen drivers. This causes build errors, so test should be
skipped for GICv3 platform too.

Same issue for regular xenvm was fixed by commit 40fe366 ("tests:
kernel: exclude xenvm from device tests"). Issue for GICv3 appeared
after migrating to HWMv2.

Signed-off-by: Dmytro Firsov <[email protected]>
@firscity firscity dismissed stale reviews from cfriedt, luca-fancellu, kartben, and lorc via dea2263 December 5, 2024 10:28
@firscity firscity force-pushed the board_xenvm_typo_fix branch 2 times, most recently from dea2263 to 8ade5c5 Compare December 5, 2024 10:29
@firscity
Copy link
Contributor Author

firscity commented Dec 5, 2024

@kartben thank you for your support, rebased

@kartben kartben merged commit b3758a7 into zephyrproject-rtos:main Dec 5, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants